As Composight considers itself to be a tools collection we strongly encourage all users to build from source for some reasons.
Nevertheless we provide some Windows x64 binaries to play around.
A reasonably stable revision of composight can be found as tar ball in the files section. In order to try the newest development check out from subversion trunk.
http://svn.code.sf.net/p/composight/code/trunk
The latest stable revision is 0.2 and can be obtained here
http://svn.code.sf.net/p/composight/code/tags/0.2.0
General Notes:
ITK 4.8.x or newer is required
composight is not yet ported to VTK 6 and Qt 5
In order to checkout the sources from SVN we recommend tortoise svn.
You will most likely use http for read-only access.
For a Windows build you will need Microsoft Visual Studio.
To Just download Composight and build it from source you can either unzip the source package or
1. Install TortoiseSVN
2. Create a Folder in the Windows explorer, right-click on it and TortoiseSVN --> Check out...
3. Enter http://svn.code.sf.net/p/composight/code/trunk
You can skip the next section and continue with the compilation instructions.
We cite the steps from SVN access for developers and SSH Key Management on the sourceforge.net Wiki.
To generate a SSH key using PuTTY where USERNAME is your sf.net account name:
Once Pageant has to be restarted every time you log in to your Windows account. To automate the Pageant startup, you might follow the instructions on this blog post: http://blog.shvetsov.com/2010/03/making-pageant-automatically-load-keys.html
We only describe the steps neede for a Visual Studio 2015 build.
We describe the steps we needed to build composight on a fresh Virtualbox Ubuntu 14.0.4 LTS.
First try to install the basic build tools and then compile ITK and VTK. Using the Qt 4 version of your Linux distribution will safe lots of time. If you run into trouble try to find compilation help for VTK and ITK first.
Install all basic build tools, CMake (2.8.12 tested, you will not have to build it from source) and Qt 4.8.
sudo apt-get install build-essential
sudo apt-get install cmake-qt-gui
sudo apt-get install libqt4-designer libqt4-dev qt4-dev-tools
sudo apt-get install subversion
Setup a build directory in your ${HOME} directory and a directory for installing all VTK/ITK/Composight binaries.
cd
mkdir devel
mkdir local
cd devel
Download the source tarball of
and put them inside ${HOME}/devel. Unpack the archives so you have something like
${HOME}/devel/VTK5.10.1
${HOME}/devel/InsightToolkit-4.8.0/
Fist make an build directory inside the source folder that we name 'release'. Then start CMake GUI. We will configure it to make an optimized build and to install itself into ${HOME}/local/ so you do not need any root access and can not accidentally mess up the system.
cd ${HOME}/devel/InsightToolkit-4.8.0/
mkdir release
cd release
Befor running CMake GUI it is necessary to tell cmake we want to use C++11 befor any default test run. This can only be done by running the command line client cmake
:
cmake -DCMAKE_CXX_FLAGS='-std=c++11' ..
cmake-gui ..
In CMake GUI:
If no errors occured you can close CMake GUI and start the build from the shell:
make -j number_of_cpu_cores
make install -j number_of_cpu_cores
will make ITK available for other projects in ${HOME}/local/lib/cmake/ITK-4.8.
You can use it not only fo composight, but also elastix, RTK, etc.
Shortcut If you do not want to debug into VTK code you can try the distributions package first. For Ubuntu LTS 14.04 it's vtk 5.8:
sudo apt-get install libvtk5.8-qt4 libvtk5-dev
Start with creating a build folder within the VTK directory.
cd ${HOME}/devel/VTK5.10.1/
mkdir release
cd release
cmake-gui ..
In CMake GUI:
-DGLX_GLXEXT_LEGACY
to the CMAKE_CXX_FLAGS text field on the right. (command line: cmake -DCMAKE_CXX_FLAGS=-DGLX_GLXEXT_LEGACY
)Back on the console run
make -j number_of_cpu_cores
If all went well you can install composight into your home folder
make -j 4 install
cd ${HOME}/devel/
svn co http://svn.code.sf.net/p/composight/code/trunk ./composight/
cd ${HOME}/devel/composight
mkdir release
cd release
cmake -DCMAKE_CXX_FLAGS='-std=c++11' ..
cmake-gui ..`In CMake GUI:
Back on the console run
make -j number_of_cpu_cores
If all went well you can install composight into your home folder
make -j 4 install
In order to launch without specifying the absolute path every time we recommend to set the $PATH variable (e.g. in ~/.bashrc)
export PATH=${HOME}/local/bin:$PATH
ITK/VTK are static builds so it is not necessary to specify their location in order to run composight programs.Try to start cpsSegmentGUI from the console as a first test and have fun...
If you want to contribute as a developer you have to use the SSH access to the svn server
It is convenient to store a public SSH key with your sourceforge account:
https://sourceforge.net/p/forge/documentation/SSH%20Keys/
The repository URL is then
svn+ssh://YOUR_SOURCEFORGE_NAME@svn.code.sf.net/p/composight/code/
make VERBOSE=1
make clean && make itkTestDriver
after activating and deactivating BUILD_TESTING (plus [Generate] each time). Using the system libjpeg, libpng and libtiff did not work out well.Tested Build environment:
- Mac OS X 10.10.5 Yosemite
- CMake 3.3.0
- XCode 7.2
- ITK 4.8.2 compiled from source
- Qt 4.8.6 provided by mac ports: qt4-mac @4.8.6_0
- VTK 5.10.1 provided by mac ports: vtk5 @5.10.1_2+qt4_mac